Hey folks,

I understand that the mirroring cadence can be troubling to you, particularly relating to building things that take a long time. The short answer is that we mirror as and when we need it for testing purposes. In this instance we need a mirror to get relevant data onto the Sisi DB so that we can perform another upgrade test to ensure that our deployment next week will be smooth and on time.

Moving forward, we are actually trying to make mirrors on a regular cadence (though there will always be exceptions) but also to increase their frequency to as much as every 2 weeks. Obviously this has some problems and we would be very receptive to hearing them (more dedicated feedback threads will go up nearer the time, but I'm now subscribed to this thread so feel free to post here too), but it also addresses one of the most oft-asked things, which is the lack of frequency of mirrors. So, with that in mind, let's hear some ideas (like Orny's above) of how we could go about mitigating the issues that come with frequent mirrors. If at all possible, bear in mind that Sisi cannot be a special little flower and have massive code differences from TQ, or it invalidates itself as a test environment.

Not going to work because somebody will assign fighters from the undock and come haze you inside the "cap free" combat area.
and if the rules kept craziness in check then we wouldnt see people getting supercap blobbed on the undock. Let's throw that out of the window. Clammoring for all deadspace officer gear was a disaster last time they did it too btw. How realistic is your "test" when you are slogging through godtanks on a rupture. Not very I'm guessing. Current system is fine.

so we are basically reprogramming the entire server to accomadate supers?
i dont see this happening.
56 drillion bugs to sort and people are worried about supers and officer modules.
no wonder bugs float thru to tq

Lets focus on the bugs and testing of broken stuff friend. Supers is last thing anyone is concerned with. The UI bug that shows full cap and shields still lurking on tq . Lets just try to get these bugs killed is all im saying.

We aren't addressing the issue of officer mods right now folks, let's stay on topic. (Also the person who said the thing about reprogramming was basically correct - it would take a bunch of coding to do what you're asking, and it still wouldn't solve any problems as people would just camp the gate.)

Accel gates are also basically a warptozero situation, aka it'll get camped and then you'll be crying about people blobbing in another thread. stuff like this just complicates things, it doesn't solve the basic problem.

I'm no coder but here's how I would pseudocode the ensuing action, should we implement this solution.

IF SubcapShipOnGate WHEN WarpImmunity=False THEN goto GateBumpAndMassiveSuperBlobAttack